Providing customer-selected solutions for multiple datacenter website hosting

ABSTRACT

Methods of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary method may comprise the steps of registering, via at least one customer interaction server, a domain name to a registrant, offering, via the at least one customer interaction server, to host at least one customer website resolving from the domain name in a first datacenter, a second datacenter, or the first datacenter and the second datacenter, provisioning, via the at least one customer interaction server, (if the registrant selects hosting the at least one customer website in the first datacenter and the second datacenter) at least one hosting server in the first datacenter and at least one hosting server in the second datacenter to host the at least one customer website; and hosting the at least one customer website on the at least one hosting server in the first datacenter and at the least one hosting server in the second datacenter.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This patent application is related to U.S. patent application Ser. No.______ entitled: “Systems for Providing Customer-Selected Solutions forMultiple Datacenter Website Hosting” concurrently filed herewith andalso assigned to The Go Daddy Group, Inc.

FIELD OF THE INVENTION

The present inventions generally relate to the field of website hostingand, more specifically, systems and methods for providingcustomer-selected solutions for multiple datacenter website hosting.

SUMMARY OF THE INVENTION

An example embodiment of a system for providing customer-selectedsolutions for multiple datacenter website hosting may comprise a firstdatacenter comprising at least one hosting server, a second datacentercomprising at least one hosting server, and a hosting services websitehosted on at least one customer interaction server. The hosting serviceswebsite may be configured to offer and implement hosting of at least onecustomer website in the first datacenter, second datacenter, or both thefirst datacenter and second datacenter. The system also may comprise anetwork communicatively coupling the first datacenter, seconddatacenter, and customer interaction server.

An example embodiment of a method for providing customer-selectedsolutions for multiple datacenter website hosting may comprise the stepsof registering a domain name to a registrant, offering to host theregistrant's website (that may resolve from the domain name) in a firstdatacenter, a second datacenter, or the first and second datacenter,provisioning (if the registrant selects hosting in both datacenters)hosting servers in both the first and second datacenter to host thecustomer website, and hosting the customer website on both provisionedservers.

The above features and advantages of the present inventions will bebetter understood from the following detailed description taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 2 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 3 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 4 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 5 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 6 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.

FIG. 7 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

FIG. 8 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

FIG. 9 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

FIG. 10 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

FIG. 11 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

FIG. 12 is a flow diagram illustrating a possible embodiment of a methodfor providing customer-selected solutions for multiple datacenterwebsite hosting.

DETAILED DESCRIPTION

The present inventions will now be discussed in detail with regard tothe attached drawing figures which were briefly described above. In thefollowing description, numerous specific details are set forthillustrating the Applicant's best mode for practicing the inventions andenabling one of ordinary skill in the art to make and use theinventions. It will be obvious, however, to one skilled in the art thatthe present inventions may be practiced without many of these specificdetails. In other instances, well-known machines, structures, and methodsteps have not been described in particular detail in order to avoidunnecessarily obscuring the present inventions. Unless otherwiseindicated, like parts and method steps are referred to with likereference numerals.

A network is a collection of links and nodes (e.g., multiple computersand/or other devices connected together) arranged so that informationmay be passed from one part of the network to another over multiplelinks and through various nodes. Examples of networks include theInternet, the public switched telephone network, the global Telexnetwork, computer networks (e.g., an intranet, an extranet, a local-areanetwork, or a wide-area network), wired networks, and wireless networks.

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweencomputer users. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information (e.g.,text, graphics, audio, video, animation, and other forms of data) atspecific locations on the Internet referred to as webpages. Websitescomprise a collection of connected or otherwise related webpages. Thecombination of all the websites and their corresponding webpages on theInternet is generally known as the World Wide Web (WWW) or simply theWeb.

Prevalent on the Web are multimedia websites, some of which may offerand sell goods and services to individuals and organizations. Websitesmay consist of a single webpage, but typically consist of multipleinterconnected and related webpages. Websites, unless extremely largeand complex or have unusual traffic demands, typically reside on asingle server and are prepared and maintained by a single individual orentity. Menus and links may be used to move between different webpageswithin the website or to move to a different website as is known in theart. The interconnectivity of webpages enabled by the Internet can makeit difficult for Internet users to tell where one website ends andanother begins.

Websites may be created using Hypertext Markup Language (HTML) togenerate a standard set of tags that define how the webpages for thewebsite are to be displayed. Users of the Internet may access contentproviders' websites using software known as an Internet browser, such asMICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX. After the browser haslocated the desired webpage, it requests and receives information fromthe webpage, typically in the form of an HTML document, and thendisplays the webpage content for the user. The user then may view otherwebpages at the same website or move to an entirely different websiteusing the browser.

Browsers are able to locate specific websites because each website,resource, and computer on the Internet has a unique Internet Protocol(IP) address. Presently, there are two standards for IP addresses. Theolder IP address standard, often called IP Version 4 (IPv4 ), is a32-bit binary number, which is typically shown in dotted decimalnotation, where four 8-bit bytes are separated by a dot from each other(e.g., 64.202.167.32). The notation is used to improve humanreadability. The newer IP address standard, often called IP Version 6(IPv6 ) or Next Generation Internet Protocol (IPng), is a 128-bit binarynumber. The standard human readable notation for IPv6 addresses presentsthe address as eight 16-bit hexadecimal words, each separated by a colon(e.g., 2EDC:BA98:0332:0000:CF8A:000C:2154:7313).

IP addresses, however, even in human readable notation, are difficultfor people to remember and use. A Uniform Resource Locator (URL) is mucheasier to remember and may be used to point to any computer, directory,or file on the Internet. A browser is able to access a website on theInternet through the use of a URL. The URL may include a HypertextTransfer Protocol (HTTP) request combined with the website's Internetaddress, also known as the website's domain name. An example of a URLwith a HTTP request and domain name is: http://www.companyname.com. Inthis example, the “http” identifies the URL as a HTTP request and the“companyname.com” is the domain name.

Domain names are much easier to remember and use than theircorresponding IP addresses. The Internet Corporation for Assigned Namesand Numbers (ICANN) approves some Generic Top-Level Domains (gTLD) anddelegates the responsibility to a particular organization (a “registry”)for maintaining an authoritative source for the registered domain nameswithin a TLD and their corresponding IP addresses. For certain TLDs(e.g., .biz, .info, .name, and .org) the registry is also theauthoritative source for contact information related to the domain nameand is referred to as a “thick” registry. For other TLDs (e.g., .com and.net) only the domain name, registrar identification, and name serverinformation is stored within the registry, and a registrar is theauthoritative source for the contact information related to the domainname. Such registries are referred to as “thin” registries. Most gTLDsare organized through a central domain name Shared Registration System(SRS) based on their TLD.

For Internet users and businesses alike, the Internet continues to beincreasingly valuable. More people use the Web for everyday tasks, fromsocial networking, shopping, banking, and paying bills to consumingmedia and entertainment. E-commerce is growing, with businessesdelivering more services and content across the Internet, communicatingand collaborating online, and inventing new ways to connect with eachother.

Some Internet users, typically those that are larger and moresophisticated, may provide their own hardware, software, and connectionsto the Internet. But many Internet users either do not have theresources available or do not want to create and maintain theinfrastructure necessary to host their own websites. To assist suchindividuals (or entities), hosting companies exist that offer websitehosting services. These hosting service providers typically provide thehardware, software, and electronic communication means necessary toconnect multiple websites to the Internet. A single hosting serviceprovider may literally host thousands of websites on one or more hostingservers.

Hosting providers often sell website hosting services based upon thecontent provider's anticipated memory and bandwidth needs. For example,a content provider may pay a lower monthly fee for 100 giga bytes (GB)of server disk space and 1000 GB of bandwidth than another contentprovider whose website may require 500 GB and 5000 GB of server diskspace and bandwidth, respectively. Content providers must carefullyevaluate their website's anticipated storage and bandwidth needs andselect their hosting plan accordingly. If they underestimate theirneeds, their website may become non-functional once their memory and/orbandwidth allotment is exceeded.

Similarly, content providers must carefully evaluate their hostingprovider's ability to quickly return requested website content to theirwebsite users. One factor that contributes to content return speed isthe physical proximity of the hosting provider's datacenters toanticipated website users. An Arizona-based business, for example, mayhave the majority of its customers (and therefore website users) locatedin Arizona. It may therefore prefer a hosting provider withArizona-based datacenters to one with datacenters in Asia.

With the proliferation of the Internet as a mechanism of commerce,however, businesses are increasingly conducting online business acrossbroad geographical boundaries. The small Arizona-based business, forexample, may increasingly see website traffic from not just Arizona, butalso New York, Europe, and Asia. Other content providers, such asindividuals, also may be experiencing an increase in suchextra-geographical website hits due to family and friends increasinglybeing dispersed throughout the world.

Ideally, hosting providers would offer content providers access todatacenters in multiple geographic locations to quickly return websitecontent to their geographically-dispersed website users. Applicant,however, has determined that presently-existing website hosting systemsand methods do not provide content providers with the ability to selectthe datacenter at which to host content, or the ability to selectcontent hosting in multiple geographies. For the foregoing reasons,there is a need for the systems and methods for providingcustomer-selected solutions for multiple datacenter website hosting, andrelated functionality, as described herein.

Systems for Providing Customer-Selected Solutions for MultipleDatacenter Website Hosting

FIG. 1 illustrates a possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting.This example embodiment may comprise a first datacenter 100 (itselfcomprising at least one hosting server 120), a second datacenter 110(also comprising at least one hosting server 120), and a hostingservices website 130 hosted on at least one customer interaction server140. The hosting services website 130 may be configured to offer andimplement hosting of at least one customer website 160 in the firstdatacenter 100, second datacenter 110, or both the first datacenter 100and second datacenter 110. A network 150 may communicatively couple thefirst datacenter 100, second datacenter 110, and customer interactionserver 140.

The first datacenter 100 and/or the second datacenter 110 may compriseany mechanism for physically—or virtually—partitioning hosting servers120 into a single, but interrelated computing center. As a non-limitingexample, the first datacenter 100 and/or the second datacenter 110 maycomprise a building or other location that stores servers and necessaryrelated systems (e.g., additional computers, clients, telecommunicationnetworks and equipment, data storage devices, power systems, securitysystems, environmental controls, switches, routers, load balancers,racks, and/or related equipment). The first datacenter 100 and/or thesecond datacenter 110 may be of any size and configuration. They maycomprise a single server rack, or an entire building, depending onsystem needs. Alternatively, they may comprise a virtual datacenter,which may be defined as a highly-distributed collection of networkedservers (perhaps connected communicatively via the network 150), whichmay perform the function of a traditional, physical datacenter. As yetanother non-limiting example, a virtual datacenter may be implementedwith a “cloud computing” solution.

Each of the at least one servers 120, the customer interaction server140, and/or any other server described herein, could be any computer orprogram that provides services to other computers, programs, or userseither in the same computer or over a computer network. As non-limitingexamples, such servers could comprise an application, communication,mail, database, proxy, fax, file, media, web, peer-to-peer, orstandalone server and may use any server format known in the art ordeveloped in the future (possibly a shared hosting server, a virtualdedicated hosting server, a dedicated hosting server, or any combinationthereof).

With a shared hosting server, many websites may reside on a singleserver. Each website may be stored in its own partition (i.e., sectionor place) on the server to keep it separate from other websites. Sharedhosting servers are the most economical hosting option because numeroushosting customers may share in server maintenance cost. Virtualdedicated servers also may comprise a single server, but one that ispartitioned into multiple (virtual) servers, each of which may have theappearance to the end user of being the users' own dedicated server.Such virtual dedicated servers may run their own operating system and beindependently rebooted. Dedicated servers generally represent the mostexpensive website hosting option. With dedicated server hosting, thehosting customer may lease a complete server that is dedicated to thatcustomer (i.e., not shared with others). This model may be more flexiblethan shared or virtual-dedicated hosting because customers may beprovided complete control over the server, including the ability tocustomize its hardware, software, and/or operating system.

The example embodiments herein place no limitation on network 150configurations or connectivity. Thus, as non-limiting examples, thenetwork 150 could comprise the Internet, a public switched telephonenetwork, a global Telex network, computer networks (e.g., an intranet,an extranet, a local-area network, or a wide-area network), wirednetworks, wireless networks, or any combination thereof. The network 150also may comprise either a single network, or multiple interconnectednetworks. All system components described herein may be communicativelycoupled to the network 150 via any method of network connection known inthe art or developed in the future including, but not limited to wired,wireless, modem, dial-up, satellite, cable modem, Digital SubscriberLine (DSL), Asymmetric Digital Subscribers Line (ASDL), Virtual PrivateNetwork (VPN), Integrated Services Digital Network (ISDN), X.25,Ethernet, token ring, Fiber Distributed Data Interface (FDDI), IP overAsynchronous Transfer Mode (ATM), Infrared Data Association (IrDA), WANtechnologies (T1, Frame Relay), Point-to-Point Protocol over Ethernet(PPPoE), the Internet, and/or any combination thereof.

The customer interaction server 140 may host a hosting services website130 accessible to content providers via the network 150. As illustratedin FIG. 1, the hosting services website 130 may be configured to offerand implement hosting of at least one customer website 160 in the firstdatacenter 100, second datacenter 110, or both the first datacenter 100and second datacenter 110. The hosting services website 130 may offersuch multi-geography hosting services via a plurality ofsoftware-enabled tools, perhaps comprising data fields, dialog boxes,drop-down menus, lists, etc., allowing the content provider to select apreferred datacenter, or multiple datacenters. Although FIG. 1illustrates the customer interaction server 140 hosting the hostingservices website 130, it alternatively may be hosted on any client orserver communicatively coupled to the network 150.

The hosting services website 130 may be configured to implement customerwebsite 160 hosting in the described datacenters (100 and/or 110) andmay comprise any software and/or script that, when executed by amicroprocessor on a client or server, may provision at least one hostingserver 120 in the first datacenter 100, at least one hosting server 120in the second datacenter 110, or both. Hosting servers 120 may beprovisioned by any method of provisioning a hosting server 120 known inthe art or developed in the future including, but not limited to imagingand/or scripting approaches, or any combination thereof. Serverprovisioning may be accomplished by configuring the server's hardwareand/or software to meet the content provider's requirements. It maycomprise installing the proper software (operating system, devicedrivers, middleware, applications, etc), configuring a boot image forthe server, and perhaps booting the newly-configured server and itsnewly-installed software, thus making the system ready for operation.The DNS A-record for the subject domain name may be updated to reflectthe IP address of the hosting server 120. Once the DNS A-record update(mapping the hosting server 120 to the domain name) propagates throughthe DNS, hosting service functionality may be fully enabled.

Where multiple hosting servers 120 are provisioned to simultaneouslyhost a customer website 160, any load balancing solution known in theart or developed in the future may be utilized including, but notlimited to, a “round robin” DNS method. Round robin DNS is a loaddistribution solution whereby multiple provisioned hosting servers 120may be configured to respond to requests according to a predeterminedstatistical model. This method works by responding to requests with alist of IP addresses (rather than a single IP address) for severalhosting servers 120. With each response, the IP address sequence in thelist is changed. Because clients generally connect with the first IPaddress on the list, subsequent connection attempts may result inconnection with a different hosting server 120, thus distributing theoverall load.

FIG. 2 illustrates an alternate possible embodiment of a system forproviding customer-selected solutions for multiple datacenter websitehosting, wherein the first datacenter 100 is located in a firstgeographic location 200 and the second datacenter 110 is located in asecond geographic location 210. The first geographic location 200 maycomprise any physical location that differs from the second geographiclocation 210. Any combination of first geographic 200 and secondgeographic location 210 may be used. As a non-limiting example, thefirst geographic location 200 may comprise North America and the secondgeographic location 210 may comprise Europe. Alternatively, the firstgeographic location 200 may comprise North America and the secondgeographic location 210 may comprise Asia.

FIG. 3 illustrates another possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting,wherein the system of FIG. 2 further comprises a routing server 300communicatively coupled to the network 150. The routing server 300 maybe configured to receive a request for content (the content being fromat least one customer website 160), and route the request to theappropriate responding datacenter (either the first datacenter 100 orthe second datacenter 110) by determining which of the datacenters mayprovide a faster response to the request.

The routing server 300 may comprise any of the server types described indetail above. It also may comprise any network router (or “switch”)known in the art or developed in the future whose software and hardwaremay be tailored to the task of routing and forwarding informationincluding, but not limited to, a provider edge router, subscriber edgerouter, inter-provider border router, core router, residential gateway,wired router, wireless router, and/or enterprise router. Anyproprietary, open source, or commercially-available (e.g., CISCO's CRS-1or CDS-IS CARRIER ROUTING SYSTEM) router may be utilized.

The routing server 300 may be configured by installing software and/orscripts that, when executed by a microprocessor on the routing server300, cause the routing server 300 to receive an incoming request,determine which datacenter will provide the quickest response, and routethe request to the appropriate server. The quickest response time may bea function of geographical proximity, and/or any other factorcontributing to delay in response time, such as system demand. As anon-limiting example, installed software and/or scripts may accomplishthis by determining the geographic origin of the request, determiningwhether the first datacenter 100 or second datacenter 110 is in closestphysical proximity to the geographic origin of the request, and routingthe request to the closest datacenter. The geographic origin of therequest may be obtained by identifying the IP address of a client makingan HTTP request (the IP address may be in the HTTP request itself) andcomparing the IP address against one of the many available geolocationdatabases, such as those provided by GEOBYTES or IP2LOCATION.

The customer website 160 hosted in the hosting servers 120 in thedatacenters (100 and 110) may comprise a single webpage or multipleinterconnected and related webpages (i.e., a website) resolving from adomain name, each of which may provide access to multimedia content(e.g., text files, audio files, video files, graphics files, executablefiles, etc.). A customer website 160 hosted in the first datacenter 100may comprise the same or different content than a customer website 160hosted in the second datacenter 110. This may allow the content providereither to have the same content delivered irrespective of geography, orto tailor content based on the Internet user's location. For example,local datacenters may return content in a native language.

FIG. 4 illustrates another possible embodiment of a system for providingcustomer-selected solutions for multiple datacenter website hosting thatmay comprise means for registering 400 a domain name to a registrant,means for offering 410 to host at least one customer website 160 (thatmay resolve from the domain name) in a first datacenter 100, a seconddatacenter 110, or both, means for provisioning 420 (if the registrantselects hosting in both datacenters) at least one hosting server 120 inthe first datacenter 100 and at least one hosting server 120 in thesecond datacenter 110 to host the customer website 160, means forhosting 430 the customer website 160 on the at least one hosting server120 in the first datacenter 100 and the at least one hosting server 120in said second datacenter 110, and a network 150 communicativelycoupling the means for registering 400, means for offering 410, meansfor provisioning 420, and means for hosting 430.

The means for registering 400 a domain name to a registrant may compriseany domain name registration system known in the art or developed in thefuture including, but not limited to, a website-enabled domain namepurchase and registration system, such as that described in detail aboveand/or may be available on GODADDY.COM's website. As a non-limitingexample, it may comprise software and/or scripts containing instructionsthat, when executed by a server's microprocessor, cause themicroprocessor to determine whether a requested or suggested domain nameis available for registration and, if available, register the domainname to the registrant.

The means for offering 410 to host a customer website 160 may compriseany system known in the art or developed in the future for offering tohost a website, such as that described in detail above and/or may beavailable on GODADDY.COM's website. As a non-limiting example, it maycomprise the customer interaction server 140 and/or hosting serviceswebsite 130 described in detail above, and/or any variation of the same.Alternatively, and as another non-limiting example, the offering means410 may comprise a telephone-based system whereby domain nameregistrants are automatically and/or manually called and offered hostingservices. Offers to host also may be made via email, instant messaging,and/or any other electronic messaging systems known in the art ordeveloped in the future.

The means for provisioning 420 hosting servers 120 may comprise anysystem for provisioning servers known in the art or developed in thefuture including, but not limited to the imaging and/or scriptingapproaches, or any combination thereof. As a non-limiting example, itmay comprise software and/or scripts containing instructions that, whenexecuted by a microprocessor on a server or client, cause themicroprocessor to provision at least one hosting server 120 in the firstdatacenter 100, at least one hosting server 120 in the second datacenter110, and/or both as described in detail above.

The means for hosting 430 the customer website 160 may comprise anysystem for hosting a website known in the art or developed in the futureincluding, but not limited to, the implementation of the at least onehosting server 120 in the first datacenter 100 and the least one hostingserver 120 in said second datacenter 110 as described in detail above.Alternatively, any hosting configuration may be utilized including, butnot limited to, systems offering virtual, dedicated, virtual-dedicated,grid, and/or cloud hosting solutions.

FIG. 5 illustrates an alternate embodiment of the system shown in FIG.4, further comprising means for receiving 500 a request for a pluralityof content from the customer website(s) 160, means for routing 510 therequest to a responding datacenter (that may be selected by determiningwhether the request will receive a faster response from the firstdatacenter 100 or the second datacenter 110), and means for returning520 content. Each of these means (500-520) may be communicativelycoupled to the network 150 as described in detail above.

The means for receiving 500 a request for website content may compriseany system known in the art or developed in the future for receiving awebsite content request including, but not limited to software and/orscripts containing instructions that, when executed by a server'smicroprocessor (perhaps a hosting server 120 or routing server 300),cause the microprocessor to interpret an incoming content request andreturn the content to the requestor. The content request may be in anyform known in the art or developed in the future including, but notlimited to HTTP, File Transfer Protocol (FTP), and/or TransmissionControl Protocol (TCP/IP).

The means for routing 510 the request to a responding datacenter maycomprise software and/or scripts containing instructions that, whenexecuted by a server's microprocessor (perhaps a hosting server 120 or arouting server 300), cause the microprocessor to determine whether therequest will receive a faster response from a first datacenter 100 or asecond datacenter 110. This may be accomplished by the routing server300 described in detail above, or perhaps by similar functionalityenabled on a hosting server 120 in a datacenter. And as illustrated inFIG. 6, one example embodiment of the routing means 510 may accomplishits task by further comprising means for determining 600 the geographicorigin of the content request, and means for identifying 610 theresponding datacenter by determining whether the first datacenter 100 orsecond datacenter 110 is in closest physical proximity to the geographicorigin of said request.

The means for returning 520 content may comprise any system or methodknown in the art or developed in the future for returning requestedwebsite content. As a non-limiting example, the returning means 520 maycomprise software and/or scripts containing instructions that, whenexecuted by a server's microprocessor (perhaps a hosting server 120),cause the microprocessor to transmit the requested content to therequesting entity. Content may be transmitted, perhaps via the network150, according to any data transmission protocol known in the art ordeveloped in the future including, but not limited to file transferprotocol (FTP).

Viable data transfer methods can generally be classified in twocategories: (1) “pull-based” data transfers where the receiver initiatesa data transmission request; and (2) “push-based” data transfers wherethe sender initiates a data transmission request. Both types areexpressly included in the embodiments illustrated herein, which also mayinclude transparent data transfers over network file systems, explicitfile transfers from dedicated file-transfer services like FTP or HTTP,distributed file transfers over peer-to-peer networks, file transfersover instant messaging systems, file transfers between computers andperipheral devices, and/or file transfers over direct modem or serial(null modem) links, such as XMODEM, YMODEM and ZMODEM. Data streamingtechnology also may be used to effectuate data transfer. A data streammay be, for example, a sequence of digitally encoded coherent signals(packets of data) used to transmit or receive information that is intransmission. Any data transfer protocol known in the art or developedin the future may be used including, but not limited to: (1) those usedwith TCP/IP (e.g., FTAM, FTP, HTTP, RCP, SFTP, SCP, or FASTCopy); (2)those used with UDP (e.g., TFTP, FSP, UFTP, or MFTP); (3) those usedwith direct modem connections; (4) HTTP streaming; (5) Tubular DataStream Protocol (TDSP); (6) Stream Control Transmission Protocol (SCTP);and/or (7) Real Time Streaming Protocol (RTSP).

The illustrated configurations set forth in FIGS. 4-6 are not meant tolimit the variety of configurations that may be implemented. Anyconfiguration of means 400-430, 510, 520, 600, and 610 that accomplishedthe functionality set forth herein may be utilized. As non-limitingexamples, the customer website 160 hosted in the first datacenter 100may comprise the same content as the customer website 160 hosted in thesecond datacenter 110. Alternatively, different content may be hosted ineach datacenter, resulting in the delivery of geographic-specificcontent. These options may allow the content provider to either have thesame content delivered irrespective of geography, or tailor contentbased on the Internet user's location. For example, local datacentersmay return content in a native language. Moreover, the means forregistering 400, means for offering 410, means for provisioning 420, andmeans for hosting 430 (and all described embodiments of the same) mayall reside on the same client, server, or other computing device.Alternatively, some (or all) of these means (400-430) may reside onseparate clients, servers, and/or other computing devices.

Methods for Providing Customer-Selected Solutions for MultipleDatacenter Website Hosting

As illustrated in FIG. 7, an example embodiment of a method forproviding customer-selected solutions for multiple datacenter websitehosting may comprise the steps of registering (perhaps via at least onecustomer interaction server 140) a domain name to a registrant (Step700) and offering (perhaps via the at least one customer interactionserver 140) to host at least one customer website 160 (that may resolvefrom the domain name) in a first datacenter 100, a second datacenter110, or both datacenters (Step 710). If the registrant selects hostingthe customer website(s) 160 in the first datacenter 100 and the seconddatacenter 110, the illustrated method also may comprise the steps ofprovisioning (perhaps by the customer interaction server 140) at leastone hosting server 120 in the first datacenter 100 and at least onehosting server 120 in the second datacenter 110 to host the customerwebsite(s) 160 (Step 730) and hosting the customer website(s) 160 on atleast one hosting server 120 in the first datacenter 100 and at theleast one hosting server 120 in the second datacenter 110 (Step 740).

Domain name registration (Step 700) may be accomplished by any domainname registration method known in the art or developed in the futureincluding, but not limited to, the registering means 400 describedabove, or perhaps via a website-enabled domain name purchase andregistration system, such as may be available on GODADDY.COM's website.Alternatively, domain name registration may be accomplished via human tohuman communication, perhaps via a telephone call or in-person meeting.Domain names may be registered by, as non-limiting examples, anyindividual or entity including, but not limited to a domain nameregistry, domain name registrar, hosting provider, and/or softwareapplication developer or distributor.

Once a domain name has been registered, the registrant (or any person orentity having control of the domain name) may be offered services forhosting at least one customer website 160 that may or may not resolvefrom the domain name (Step 710). This website hosting offer may be madein any manner known in the art or developed in the future for extendingan offer including, but not limited to the offering means 410 describedin detail above. As a further non-limiting example, this offer may bemade via the at least one customer interaction server 140, perhaps bydisplaying an offer on a hosting services website 130 upon completion ofdomain name registration (Step 700). Alternatively, the customerinteraction server 140 may send the offer via an electroniccommunication (e.g., email message, SMS message, and/or other text,video, or audio message) to the domain name registrant. The offer alsomay be accomplished via human to human communication, perhaps via atelephone call or in-person meeting. Irrespective of the offering methodused, the offer itself may provide the domain name registrant with theoption to host his customer website 160 in a first datacenter 100, asecond datacenter 110, or both the first datacenter 100 and the seconddatacenter 110. FIG. 1 illustrates a possible embodiment of a hostingservices website 130 providing such options.

If the offer is accepted—and the registrant selects the option ofhosting the customer website(s) 160 in both the first datacenter 100 andthe second datacenter 110—at least one hosting server 120 in both thefirst datacenter 100 and the second datacenter 110 may be provisioned tohost the customer website 160 (Step 730). Hosting servers 120 may beprovisioned, perhaps via the at least one customer interaction server140 or the hosting servers 120 themselves, via any of the systems and/ormethods of server provisioning described above including, but notlimited to, the provisioning means 420. Once the hosting servers 120have been provisioned, the customer website 160 may be hosted (Step 740)on at least one hosting server 120 in the first datacenter 100 and atleast one hosting server 120 in the second datacenter 110. Hosting maybe accomplished by any of the methods and/or systems known in the art ordeveloped in the future including, but not limited to, those describedin detail above, such as the hosting means 430.

FIG. 8 illustrates an alternate embodiment of the method illustrated inFIG. 7, further comprising the steps of receiving (perhaps via at leastone routing server 300), a request for a plurality of content from thecustomer website(s) 160 (Step 800), routing the request (perhaps by arouting server 300) to a responding datacenter, which may be either thefirst datacenter 100 or said second datacenter 110, depending on whichdatacenter is determined to provide a quicker request response (therequest may be routed to the quicker-responding datacenter) (Step 810),and returning the content to the requester, perhaps by a hosting server120 in the responding datacenter (Step 820).

A content request may be received (Step 800), by any system or methodknown in the art or developed in the future for receiving a websitecontent request including, but not limited to software and/or scriptscontaining instructions that, when executed by a server's microprocessor(perhaps a hosting server 120 or routing server 300), cause themicroprocessor to interpret an incoming content request and return thecontent to the requestor. The content request may be in any form knownin the art or developed in the future including, but not limited toHTTP, File Transfer Protocol (FTP), and/or Transmission Control Protocol(TCP/IP).

The content request then may be routed to a responding datacenter (Step810). This step may be accomplished by any system or method known in theart or developed in the future for determining whether the firstdatacenter 100 or second datacenter 110 would provide a quicker requestresponse and routing the request to the responding datacenter including,but not limited to, the routing server 300 and/or routing means 510described in detail above. The routing server 300 may be configured toaccomplish this step by installing the above-described software and/orscripts on the routing server 300. The quickest response time may be afunction of geographical proximity, or any other factor contributing todelay in response time, such as system demand.

As a non-limiting example illustrated in FIG. 9, the routing step (Step810) also may be accomplished by determining the geographic origin ofthe request (Step 900), determining whether the first datacenter 100 orsecond datacenter 110 is in closest physical proximity to the geographicorigin of the request (Step 910), and routing the request to the closestdatacenter (Step 810). As a non-limiting example, the geographic originof the request may be obtained by identifying the IP address of a clientmaking an HTTP request (the IP address may be in the HTTP requestitself) and comparing the IP address against one of the many availablegeolocation databases, such as those provided by GEOBYTES orIP2LOCATION. This physical location then may be compared to the knownlocations of the first datacenter 100 and second datacenter 110 and thecontent request may be routed to the closest datacenter (i.e.,responding datacenter). Routing step 810 also may be implemented by anysystem or method of geographical load balancing known in the art ordeveloped in the future including, but not limited to, theimplementation of a Content Delivery Network (CDN) for web acceleration,such as may be offered commercially by AKAMAI, LIMELIGHT, and/orCDNETWORKS.

FIG. 10 illustrates a variation of the method illustrated in FIG. 9,wherein offering step 710 is accomplished by providing a hostingservices website 130 (Step 1000) as described in detail above.

FIGS. 11 and 12 illustrate a method for providing customer-selectedsolutions for multiple datacenter website hosting similar to thoseillustrated in FIGS. 7 and 9, wherein the domain name registration step(700) has been replaced with the step of receiving (perhaps by at leastone customer interaction server 140) a request for hosting services froma domain name registrant (Step 1100). Whereas the methods illustrated inFIGS. 7-10 may be performed by a domain name registrar as part of thedomain name registration process, these illustrated embodiments (FIGS.11 and 12) may provide tools for non-domain name registering entities toprovide the services described herein. For example, a domain nameregistrant may register a domain name with his registrar, and thencontact a hosting provider (that may not also be a domain nameregistrar) to request hosting services (Step 1100). The hosting providerthen may implement the disclosed methods by following the abovedescribed steps (710-910).

An Example Use of Systems and Methods for Providing Customer-SelectedSolutions for Multiple Datacenter Website Hosting

The systems and methods described herein may be used in many waysincluding to, among other things, allow domain name registrants and/orhosting service customers to select the geographic location where theirwebsite(s) 160 may be hosted, perhaps to optimize request response time,or to geographically customize website 160 content.

As a non-limiting example of how such systems and methods may be used,an Arizona-based business owner may, via the browser on his laptopcomputer that may be wirelessly connected to the Internet (i.e., thenetwork 150), navigate to a domain name registrar and hosting provider'swebsite 130, such as (GODADDY.COM's website) and register a domain name(e.g., “widgets.com”) (Step 700). During the registration process, thedomain name registrar then may offer to host any website 160 that theregistrant may want to associate with the domain name “widgets.com”(Step 710). The offer may appear as a pop up window on the hostingservices website 130 that asks the registrant to select where he wouldlike his website hosted: in a datacenter located in North America,Europe, or both.

Because the registrant's business (and most of his customers) may belocated in Arizona, but he also may have a niche market and customerbase in Germany (that requires a German language website), he may selectthe “both” option, wishing to host his website 160 in both North Americaand Europe. Software running on the customer interaction server 140(that hosts the hosting services website 130) may then provision ahosting server 120 in a North American datacenter and another hostingserver 120 in a European datacenter to host the customer's website 160(Step 730). Once server provisioning is complete, the registrant mayupload website 160 content to each hosting server 120, withEnglish-language content being hosted in the North American datacenterand German-language content being hosted in the European datacenter(Step 740).

When an HTTP request seeking the website located at www.widgets.com isreceived by a routing server 300 (Step 800), software running on therouting server 300 may determine (by analyzing the HTTP request) the IPaddress of the requesting client. The IP address may then be comparedagainst an online geolocation database, such as that provided byGEOBYTES, which maps IP address to geographic location. If thegeographic location is determined to be in Germany, the routing server300 may route the HTTP request to the hosting server 120 in the Europeandatacenter (Step 810), which then may respond to the HTTP request withGerman-language website 160 content.

Other embodiments and uses of the above inventions will be apparent tothose having ordinary skill in the art upon consideration of thespecification and practice of the inventions disclosed herein. Thespecification and examples given should be considered exemplary only,and it is contemplated that the appended claims will cover any othersuch embodiments or modifications as fall within the true scope of theinventions.

The Abstract accompanying this specification is provided to enable theUnited States Patent and Trademark Office and the public generally todetermine quickly from a cursory inspection the nature and gist of thetechnical disclosure and in no way intended for defining, determining,or limiting the present inventions or any of its embodiments.

1. A method, comprising the steps of: A) registering, via at least onecustomer interaction server computer, a domain name to a registrant; B)offering, via said at least one customer interaction server computer, tohost at least one customer website resolving from said domain name in afirst datacenter, a second datacenter, or said first datacenter and saidsecond datacenter; C) if said registrant selects hosting said at leastone customer website in said first datacenter and said seconddatacenter, provisioning, via said at least one customer interactionserver computer, at least one hosting server computer in said firstdatacenter and at least one hosting server computer in said seconddatacenter to host said at least one customer website; and D) hostingsaid at least one customer website on said at least one hosting servercomputer in said first datacenter and at said least one hosting servercomputer in said second datacenter.
 2. The method of claim 1, whereinsaid first datacenter is located in a first geographic location and saidsecond datacenter is located in a second geographic location.
 3. Themethod of claim 2, wherein said first geographic location comprisesNorth America and said second geographic location comprises Europe. 4.The method of claim 2, wherein said first geographic location comprisesNorth America and said second geographic location comprises Asia.
 5. Themethod of claim 2, further comprising the steps of: E) receiving, via atleast one routing server computer, a request for a plurality of saidcustomer website's content; F) routing, by said at least one routingserver computer, said request to a responding datacenter selected fromthe group consisting of said first datacenter and said second datacenterby determining whether said request will receive a faster response fromsaid first datacenter or said second datacenter; and G) returning, by atleast one hosting server computer in said responding datacenter, saidplurality of content.
 6. The method of claim 5, wherein said routingstep F) further comprising the steps of: i) determining, by said atleast one routing server computer, a geographic origin of said request;ii) identifying, by said at least one routing server computer, saidresponding datacenter by determining whether said first datacenter orsaid second datacenter is in closest physical proximity to saidgeographic origin of said request; and iii) routing, by said at leastone routing server computer, said request to said response datacenter.7. The method of claim 6, wherein said at least one customer websitehosted in said first datacenter comprises the same content as said atleast one customer website hosted in said second datacenter.
 8. Themethod of claim 6, wherein said at least one customer website hosted insaid first datacenter comprises different content than said at least onecustomer website hosted in said second datacenter.
 9. The method ofclaim 6, wherein said at least one customer interaction server computer,said at least one hosting server computer, and said at least one routingserver computer comprise the same server computer.
 10. The method ofclaim 6, wherein said at least one customer interaction server computer,said at least one hosting server computer, and said at least one routingserver computer comprise a plurality of different server computers. 11.The method of claim 6, wherein said offering step B) is accomplished byproviding a hosting services website comprising means for saidregistrant to select hosting said at least one customer website in saidfirst datacenter and said second datacenter.
 12. A method, comprisingthe steps of: A) receiving, by at least one customer interaction servercomputer, a request for hosting services from a registrant of a domainname; B) offering, via said at least one customer interaction servercomputer, to host at least one customer website resolving from saiddomain name in a first datacenter, a second datacenter, or said firstdatacenter and said second datacenter; C) if said registrant selectshosting said at least one customer website in said first datacenter andsaid second datacenter, provisioning, via said at least one customerinteraction server computer, at least one hosting server computer insaid first datacenter and at least one hosting server computer in saidsecond datacenter to host said at least one customer website; and D)hosting said at least one customer website on said at least one hostingserver computer in said first datacenter and at said least one hostingserver computer in said second datacenter.
 13. The method of claim 12,wherein said first datacenter is located in a first geographic locationand said second datacenter is located in a second geographic location.14. The method of claim 13, wherein said first geographic locationcomprises North America and said second geographic location comprisesEurope.
 15. The method of claim 13, wherein said first geographiclocation comprises North America and said second geographic locationcomprises Asia.
 16. The method of claim 13, further comprising the stepsof: E) receiving, via at least one routing server computer, a requestfor a plurality of said customer website's content; F) routing, by saidat least one routing server computer, said request to a respondingdatacenter selected from the group consisting of said first datacenterand said second datacenter by determining whether said request willreceive a faster response from said first datacenter or said seconddatacenter; and G) returning, by said at least one hosting servercomputer in said responding datacenter, said plurality of content. 17.The method of claim 16, wherein said routing step F) further comprisingthe steps of: i) determining, by said at least one routing servercomputer, a geographic origin of said request; ii) identifying, by saidat least one routing server computer, said responding datacenter bydetermining whether said first datacenter or said second datacenter isin closest physical proximity to said geographic origin of said request;and iii) routing, by said at least one routing server computer, saidrequest to said response datacenter.
 18. The method of claim 17, whereinsaid at least one customer website hosted in said first datacentercomprises the same content as said at least one customer website hostedin said second datacenter.
 19. The method of claim 17, wherein said atleast one customer website hosted in said first datacenter comprisesdifferent content than said at least one customer website hosted in saidsecond datacenter.
 20. The method of claim 17, wherein said at least onecustomer interaction server computer, said at least one hosting servercomputer, and said at least one routing server computer comprise thesame server computer.
 21. The method of claim 17, wherein said at leastone customer interaction server computer, said at least one hostingserver computer, and said at least one routing server computer comprisea plurality of different servers computers.
 22. The method of claim 17,wherein said offering step B) is accomplished by providing a hostingservices website comprising means for said registrant to select hostingsaid at least one customer website in said first datacenter and saidsecond datacenter.